Let's first check in #9617

After reading latest comment to #9617 I tested it one more time and indeed I was able to controll the device. I'm not sure why it didn't work to me before. Maybe I was on some different branch of some other dependency...
The only issue I see now, are the errors appearing in the log, which originate from the tzLocal.led_control function, trying to read unsupported attributes.
I'm new to this project, so I'm sorry if my suggestions are off, but do you think it's good enough or should we aim to clean that up?
The code of the converter, before the commit bf81743 seems much more clean to me and in my case it needed only slight tweaking to start working properly.
On the other hand tzLocal.led_control function is quite complex and making it aware of which attributes are supported by which devices would require some carefull refactoring.

I would keep it as is, it seems this device requires specific Tuya commands.

Could you please help me understand what type of speciffic commands could it need? I spent some time trying to tune the setup for my devices and I'm stil at the position that the "modern extend" version works pretty well for me.

I indeed found one issue, with how those bulbs handle "moveToLevelWithOnOff" command". It works fine for the levels higher than 20, but if I set anything lower it can turn off on random (more ofthen than not). Maybe this is also simmilar case as described in another thread?
I created a workaround in my branch (2ae0db3) but I can't tell for sure it won't mess up some other parts of the logic.
Currently I'm more or less sattisfied with this version, because I could also enable "powerOnBehavior", which the bulbs also seem to support. I wonder if the guy for the other thread would like to test this commit and check if it solves the issues he had previously.

Let's try, thanks!